Skip to content

update dependencies, migrate build-backend to hatchling #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

update dependencies, migrate build-backend to hatchling #29

wants to merge 4 commits into from

Conversation

alexrashed
Copy link
Member

@alexrashed alexrashed commented Aug 20, 2025 •
edited
Loading

Motivation

We are currently planning to add additional support for hatchling, such that entrypoints can dynamically be detected when hatchling is being used as a build-backend for a project which uses plux.
Similar to pytest, hatchling uses pluggy, and the old pytest version caused a version conflict.
This is why I updated all dependencies, moved from setup.cfg to pure pyproject.toml, and along the way I ended up migrating the whole project to hatchling.
Please let me know if I went a bit too far here, but hatchling seems to be the clear successor of setuptools, so it seemed just natural to implement the migration.

Changes

  • Drop support for Python 3.8 (EOL was October 2024).
  • Add official support for Python 3.13.
  • Migrate from setup.cfg to pure pyproject.toml and remove setup.py.
  • Upgrade all dependency pins.
  • Migrate the build backend from setuptools to hatchling.

@alexrashed alexrashed force-pushed the switch-to-hatchling branch from 1810dda to bcc7752 Compare August 20, 2025 15:28
@thrau
Copy link
Member

thrau commented Oct 13, 2025

@alexrashed LGTM! i'm happy to switch to hatchling if it doesn't cause any downstream issues! would you want to merge this?

@alexrashed
Copy link
Member Author

alexrashed commented Oct 20, 2025 •
edited
Loading

@thrau Sorry for having this lying around for so long. I think this PR could be merged as it is, as it really just changes the way how plux is being built, now how it integrates with setuptools.
However, when continuing on this PR I was exploring how plux could be integrated into hatchling instead of setuptools when discovering the plugins and was facing some conceptual issues due to the difference in the build process.
I think this PR does have some value already, but the actual hatchling integration of plux would be the real deal 😛
What do you think? How should we proceed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@thrau thrau Awaiting requested review from thrau thrau will be requested when the pull request is marked ready for review thrau is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@alexrashed @thrau